Security and maintenance

New security sets for staff-only access

New preconfigured security access sets let you easily restrict folders, objects, and content for use by staff users only. You can grant access to all of your staff, or you can also grant it to a specific User Class: Full or Casual. These new security sets are available throughout iMIS, whenever you see the option to configure Access Settings.

Database sa password no longer required

You can now install and run iMIS without having to give your database's sa (System Administrator) user password to anyone. You can specify a non-sa sysadmin account for installation and a regular login for iMIS to run under. The installer uses the specified system administrator account to do tasks such as attaching the database, but it does not persist this account's information anywhere. After installation completes, you may delete the sysadmin account if you supplied a separate login for iMIS to run under, with db_owner permissions on the iMIS database.

Upgrade preserves web.config settings

Upgrades from version 15.2.13 and later now update your existing web.config file directly. Rather than overwriting the file, the upgrader makes its changes in-place, preserving your database connection strings and indexing search service while it adds any new config file entries needed. The upgrader also creates a webref.config reference file in the same directory, which shows the configuration for a new installation to help you to debug any issues you encounter with your merged file.

Database Maintenance utility replaces DB Repair

With this release, the "DB Repair" tool is now the iMIS Database Maintenance utility. This name change both reflects and supports the tool's expanding role in helping you to manage your iMIS database. All iMIS utilities are available in your ASI program group.

Images upload to same system-defined path

Toward the goal of making it easier for you to organize your site images where they cannot be overwritten, iMIS now uses one system-defined path for all of the image files that you upload. You can change this path, which is defined as the CM.ImagePath in your SystemConfig table. This setting is honored by the Image Manager (Content Management > Manage images) and by all iParts that reference uploaded images, such as Contact Profile Picture Display (exception: Content Block Editor stores images in the database). Theme-related images are still managed within appropriate theme folders.

Change History Display - logging specific objects and tables

The Change History Display iPart can now display data changes made to specific dynamic business objects in the Panel Editor in which the log all changes option is enabled.